5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
- Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-10: Inquiry Processes

Inquiry Process Specifications


Inquiry process specifications establish the general attributes of an inquiry process. They include such specifications as the inquiry print file, if any, the process control file, the name of the inquiry, and format characteristics. The Inquiry Processes screen is shown below.

Inquiry Processes Screen

The Inquiry Processes screen contains the following inquiry-specific fields.

Process Name identifies a specific process that is unique within type and application.

Control File identifies a file by application ID and file name that is to be automatically managed by APPX during the execution of this process. APPX automatically reads the process control file (PCF) during inquiry process execution.

Width indicates the maximum number of characters across, or in other words the number of columns, to allocate for each row in the report format. APPX uses the value you enter here to produce standard images of the proper width. If blank, the default width of the form that the report prints on defaults to the form width which is defined in system administration. If the form is narrower than the width of the formatted report, APPX truncates the inquiry. If the form is wider than the width of the report, however, APPX uses the larger width for standard images, but does not expand the format of the report itself. The default is 80.

PageH determines whether or not APPX automatically prints a page heading standard image. If 'yes' , this image prints before any Start of Page frames for the report. Be careful not to also explicitly define a Start of Page frame with a page heading standard image, which could cause the standard image to print twice at the top of each page in the report. If 'no' , you can explicitly define a Start of Page frame with a page heading standard image or, alternatively, define your own page heading using a Start of Page frame. The default is 'yes'.

ColH determines whether or not APPX automatically prints a Start of Page frame with a column heading standard image. APPX generates column headings based upon specifications in the data dictionary for each item included in the inquiry image. If 'yes' , this image prints after any Start of Page frames for the report. Be careful not to also explicitly define a Start of Page frame with a column heading standard image, which would cause the standard image to print twice for each page in the report. If 'no' , you can explicitly define a Start of Page frame with a column heading standard image or, alternatively, define your own column headings using a Start of Page frame. The default is 'yes'. Refer to Standard Column Heading Image for additional information.

Sep  (Separator) identifies one alphanumeric character that prints continuously across the report to separate standard page headings,page frames, and standard column headings from the body of the report. If blank, APPX does not print a heading separator. The default is =.

Options are indicators that are present whenever documentation (T), rules (R), or additional attributes (AA) have been defined for this process.

The following options as described in the corresponding sections are available on the Inquiry Processes screen:

Additional Attributes

Rules

Documentation

Security

In addition, the menu bar provides the following pulldown menus:

Toolbox - Same as the Process Toolbox Pulldown Menu.

Jump to - Same as the Process Jump to Pulldown Menu.

Application Design Manual                                         "Powered by Appx Software"

1106

©2006 By APPX Software, Inc. All Rights Reserved